Repository navigation
Fix resume, proxy, 403 and installer fixes across TUI, extensions and GUI - #425
Conversation
ja7ad
commented
Nov 11, 2026
ja7ad
commented
- Resolves bug: doesnt detect browser proxy #381
- Resolves bug: unexpected behavior when resuming the queue in hydra tui #396
- Resolves bug: Installer fails to overwrite the old DisplayVersion registry key #377
- Resolves bug: file won't download, "server answered 403 forbidden" #398
- Resolves bug:YouTube Downloads Report "Resume Capability: No" While Regular Downloads Support Resuming #328
Reads fixed-server rules and evaluates PAC scripts in an offscreen sandbox so downloads follow the browser's proxy. Bumps the extensions to 0.4.2. Fixes #381
Keeps each track in a scratch folder beside the .part so a rerun continues where it stopped, and clears it on remove or redownload. Refs #328
A server that omits its intermediate now verifies like it does in a browser; fetched certs must still chain to a bundled root.
![accesslint[bot]](https://avatars.githubusercontent.com/in/1502?s=60&v=4){kind=small}
There was a problem hiding this comment.
Found 11 issues across 6 rules (7 WCAG, 4 Best Practice).
Reviewed by AccessLint, which checks every pull request for accessibility issues.
| @@ -0,0 +1,10 @@ | |||
| <!doctype html> | |||
| <html> | |||
There was a problem hiding this comment.
WCAG 2.4.2: Document is missing a <title> element.
Documents must have a <title> element to provide users with an overview of content.
Details
Screen reader users rely on page titles to identify and navigate between tabs/windows. Add a descriptive <title> element in <head> that summarizes the page purpose. Keep titles unique across the site, placing specific content before the site name (e.g., 'Contact Us - Acme Corp').
WCAG 2.4.1: Page has no mechanism to bypass repeated content. Add a <main> landmark or skip link.
Page must have a mechanism to bypass repeated blocks of content.
Details
Missing: no landmarks (<main>, <nav>, <header>, <footer>), no skip link, no headings
Keyboard users must be able to skip repetitive content like navigation. Provide a skip link at the top of the page that links to the main content (e.g., <a href="#main">Skip to main content</a>), or use a <main> landmark. Screen readers can jump directly to landmarks, so a properly marked-up <main> element satisfies this requirement.
Best Practice: Page does not contain a level-one heading.
Page should contain a level-one heading.
Details
A level-one heading (<h1> or role='heading' with aria-level='1') helps users understand the page topic and provides a landmark for screen reader navigation. Each page should have at least one level-one heading that describes the main content, typically matching or similar to the page title.
Best Practice: Page has no main landmark.
Page should have exactly one main landmark.
Details
The main landmark contains the primary content of the page. Screen readers allow users to jump directly to main content. Use a single <main> element (or role='main') to wrap the central content, excluding headers, footers, and navigation.
WCAG 3.1.1: <html> element missing lang attribute.
The <html> element must have a lang attribute.
Details
Screen readers use the lang attribute to determine which language rules and pronunciation to use. Without it, content may be mispronounced. Set lang to the primary language of the page using a BCP 47 code (e.g., 'en' for English, 'es' for Spanish, 'fr' for French, 'de' for German, 'ja' for Japanese, 'zh' for Chinese, 'pt' for Portuguese, 'ar' for Arabic).
| <meta charset="utf-8" /> | ||
| </head> | ||
| <body> | ||
| <iframe id="pac" src="pac-sandbox.html"></iframe> |
There was a problem hiding this comment.
WCAG 4.1.2: Frame is missing an accessible name. Add a title attribute.
Frames must have an accessible name.
Details
src: "pac-sandbox.html"
Screen readers announce frame titles when users navigate frames. Add a title attribute to <iframe> and <frame> elements that describes the frame's purpose (e.g., <iframe title='Video player'>). Avoid generic titles like 'frame' or 'iframe'. If the frame is decorative, use aria-hidden='true'.
| @@ -0,0 +1,7 @@ | |||
| <!doctype html> | |||
| <html> | |||
There was a problem hiding this comment.
WCAG 2.4.2: Document is missing a <title> element.
Documents must have a <title> element to provide users with an overview of content.
Details
Screen reader users rely on page titles to identify and navigate between tabs/windows. Add a descriptive <title> element in <head> that summarizes the page purpose. Keep titles unique across the site, placing specific content before the site name (e.g., 'Contact Us - Acme Corp').
WCAG 2.4.1: Page has no mechanism to bypass repeated content. Add a <main> landmark or skip link.
Page must have a mechanism to bypass repeated blocks of content.
Details
Missing: no landmarks (<main>, <nav>, <header>, <footer>), no skip link, no headings
Keyboard users must be able to skip repetitive content like navigation. Provide a skip link at the top of the page that links to the main content (e.g., <a href="#main">Skip to main content</a>), or use a <main> landmark. Screen readers can jump directly to landmarks, so a properly marked-up <main> element satisfies this requirement.
Best Practice: Page does not contain a level-one heading.
Page should contain a level-one heading.
Details
A level-one heading (<h1> or role='heading' with aria-level='1') helps users understand the page topic and provides a landmark for screen reader navigation. Each page should have at least one level-one heading that describes the main content, typically matching or similar to the page title.
Best Practice: Page has no main landmark.
Page should have exactly one main landmark.
Details
The main landmark contains the primary content of the page. Screen readers allow users to jump directly to main content. Use a single <main> element (or role='main') to wrap the central content, excluding headers, footers, and navigation.
WCAG 3.1.1: <html> element missing lang attribute.
The <html> element must have a lang attribute.
Details
Screen readers use the lang attribute to determine which language rules and pronunciation to use. Without it, content may be mispronounced. Set lang to the primary language of the page using a BCP 47 code (e.g., 'en' for English, 'es' for Spanish, 'fr' for French, 'de' for German, 'ja' for Japanese, 'zh' for Chinese, 'pt' for Portuguese, 'ar' for Arabic).
Bumps rustix to 1.1.6 and async-executor to 1.14.1; accepts the unmaintained pin-utils reached through iced's wasmtimer.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #425 +/- ##
==========================================
+ Coverage 83.73% 83.85% +0.12%
==========================================
Files 111 111
Lines 50251 50686 +435
==========================================
+ Hits 42078 42504 +426
- Misses 8173 8182 +9
🚀 New features to boost your workflow:
|
